Device, Method, and Graphical User Interface for Controlling Multiple Devices in an Accessibility Mode

ABSTRACT

In accordance with some embodiments, a method is performed at a first device with one or more processors, non-transitory memory, and a display. The method includes displaying, on the display, a device control transfer affordance while operating the first device based on user input from an input device that is in communication with the first device. The method includes receiving a device control transfer user input from the input device selecting the device control transfer affordance that is displayed on the display of the first device. In response to receiving the device control transfer user input, the method includes configuring a second device to be operated based on user input from the input device and ceasing to operate the first device based on user input from the input device.

CROSS-REFERENCE TO RELATED-APPLICATIONS

This application claims the benefit of U.S. Provisional Patent App. No.62/348,884, filed on Jun. 11, 2016, which is incorporated by referencein its entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that include a user interface for controllingmultiple devices in an accessibility mode.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Example touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Example manipulations include adjusting the position and/or size of oneor more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Example user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture, iPhoto, Photos fromApple Inc. of Cupertino, Calif.), a digital content (e.g., videos andmusic) management application (e.g., iTunes from Apple Inc. ofCupertino, Calif.), a drawing application, a presentation application(e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But people with limited motor skills, such as those with certain fingeror hand impairments, may find performing certain gestures difficult andmay employ alternative input devices to control an electronic device.However, people with limited motor skills may have multiple electronicdevices and only a single easily accessible alternative input device andmay have difficulty reconfiguring the input device to control differentelectronic devices, e.g., by disconnecting the input device from a firstdevice and connecting the input device to a second device.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for controlling multiple devices in anaccessibility mode. Such methods and interfaces optionally complement orreplace conventional methods for controlling multiple devices in anaccessibility mode. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at a devicewith one or more processors, non-transitory memory, and a display. Themethod includes: displaying, on the display, a device control transferaffordance while operating the first device based on user input from aninput device that is in communication with the first device, receiving adevice control transfer user input from the input device selecting thedevice control transfer affordance that is displayed on the display ofthe first device, and, in response to receiving the device controltransfer user input, configuring a second device to be operated based onuser input from the input device and ceasing to operate the first devicebased on user input from the input device.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a user interface, one or more inputunits configured to receive user inputs, and a processing unit coupledwith the display unit and the one or more input units. The processingunit is configured to display, on the display unit, a device controltransfer affordance while operating the first device based on user inputfrom an input device that is in communication with the first device,receive a device control transfer user input from the input deviceselecting the device control transfer affordance that is displayed onthe display of the first device, and, in response to receiving thedevice control transfer user input, configure a second device to beoperated based on user input from the input device and ceasing tooperate the first device based on user input from the input device.

In accordance with some embodiments, an electronic device includes adisplay, one or more processors, non-transitory memory, and one or moreprograms; the one or more programs are stored in the non-transitorymemory and configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a non-transitory computer readablestorage medium has stored therein instructions which when executed byone or more processors of an electronic device with a display and aninput device, cause the device to perform or cause performance of theoperations of any of the methods described herein. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, a memory, and one or more processors to execute one ormore programs stored in the non-transitory memory includes one or moreof the elements displayed in any of the methods described above, whichare updated in response to inputs, as described in any of the methodsdescribed herein. In accordance with some embodiments, an electronicdevice includes: a display, and means for performing or causingperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, an information processing apparatus,for use in an electronic device with a display, includes means forperforming or causing performance of the operations of any of themethods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with faster, more efficient methodsand interfaces for controlling multiple devices in an accessibilitymode, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for controlling multipledevices in an accessibility mode.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an example user interface for a menu of applicationson a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an example user interface for a multifunction devicewith a touch-sensitive surface that is separate from the display inaccordance with some embodiments.

FIG. 5 illustrate an example environment including multiple devices inaccordance with some embodiments.

FIGS. 6A-6BD illustrate example user interfaces for controlling multipledevices in an accessibility mode in accordance with some embodiments.

FIGS. 7A-7G are flow diagrams illustrating a method of controllingmultiple devices in an accessibility mode in accordance with someembodiments.

FIG. 8 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The use of electronic devices with touch-based user interfaces (e.g.,devices such as the iPhone®, iPod Touch®, and iPad® devices from AppleInc. of Cupertino, Calif.) has increased significantly in recent years.These devices use touch-sensitive surfaces, such as a touch screendisplay or a touch pad, as the main input for manipulating userinterface objects on a display and/or controlling the device. Peoplewith limited motor skills, such as those with certain finger or handimpairments, may find applying force or pressure to the touch-sensitivesurface difficult, if not impossible, and may employ alternative inputdevices to control the device. However, people with limited motor skillsmay have multiple electronic devices and only a single easily accessiblealternative input device and may have difficulty reconfiguring the inputdevice to control different electronic devices, e.g., by disconnectingthe input device from a first device and connecting the input device toa second device.

Described below are methods and devices that enable users who cannoteasily reconfigure an input device to work with a different device tonevertheless operate multiple devices with a single input device. Insome embodiments, as described below, an electronic device displays, aspart of a user interface, a selectable affordance for transferringcontrol from a first device to a second device (and/or back to the firstdevice or to third device).

Below, FIGS. 1A-1B, 2, 3, and 4A-4B provide a description of exampledevices. FIG. 5 illustrates an environment with multiple devices. FIGS.6A-6BD illustrate example user interfaces for controlling multipledevices in an accessibility mode. FIGS. 7A-7G illustrate a flow diagramof a method of controlling multiple devices in an accessibility mode.The user interfaces in FIGS. 6A-6BD are used to illustrate the processesin FIGS. 7A-7G.

Example Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Example embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 120 and the peripheralsinterface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips. RF (radio frequency) circuitry 108 receives and sendsRF signals, also called electromagnetic signals. RF circuitry 108converts electrical signals to/from electromagnetic signals andcommunicates with communications networks and other communicationsdevices via the electromagnetic signals. RF circuitry 108 optionallyincludes well-known circuitry for performing these functions, includingbut not limited to an antenna system, an RF transceiver, one or moreamplifiers, a tuner, one or more oscillators, a digital signalprocessor, a CODEC chipset, a subscriber identity module (SIM) card,memory, and so forth. RF circuitry 108 optionally communicates withnetworks, such as the Internet, also referred to as the World Wide Web(WWW), an intranet and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN) and/or ametropolitan area network (MAN), and other devices by wirelesscommunication. The wireless communication optionally uses any of aplurality of communications standards, protocols and technologies,including but not limited to Global System for Mobile Communications(GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packetaccess (HSDPA), high-speed uplink packet access (HSUPA), Evolution,Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long termevolution (LTE), near field communication (NFC), wideband code divisionmultiple access (W-CDMA), code division multiple access (CDMA), timedivision multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi)(e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoW),Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol(IMAP) and/or post office protocol (POP)), instant messaging (e.g.,extensible messaging and presence protocol (XMPP), Session InitiationProtocol for Instant Messaging and Presence Leveraging Extensions(SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or ShortMessage Service (SMS), or any other suitable communication protocol,including communication protocols not yet developed as of the filingdate of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an example embodiment, a point ofcontact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an example embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, haptic feedback module (orset of instructions) 133, text input module (or set of instructions)134, Global Positioning System (GPS) module (or set of instructions)135, and applications (or sets of instructions) 136. Furthermore, insome embodiments, memory 102 stores device/global internal state 157, asshown in FIGS. 1A and 3. Device/global internal state 157 includes oneor more of: active application state, indicating which applications, ifany, are currently active; display state, indicating what applications,views or other information occupy various regions of touch-sensitivedisplay system 112; sensor state, including information obtained fromthe device's various sensors and other input or control devices 116; andlocation and/or positional information concerning the device's locationand/or attitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 146, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesexecutable instructions that allow the user to access, browse, receive(e.g., by streaming and/or download), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or viaexternal port 124), send an e-mail with a link to a particular onlinevideo, and otherwise manage online videos in one or more file formats,such as H.264. In some embodiments, instant messaging module 141, ratherthan e-mail client module 140, is used to send a link to a particularonline video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating example components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an example multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an example user interface for a menu of applicationson portable multifunction device 100 in accordance with someembodiments. Similar user interfaces are, optionally, implemented ondevice 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser”; and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod”; and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text”;        -   Icon 426 for calendar module 148, labeled “Calendar”;        -   Icon 428 for image management module 144, labeled “Photos”;        -   Icon 430 for camera module 143, labeled “Camera”;        -   Icon 432 for online video module 155, labeled “Online            Video”;        -   Icon 434 for stocks widget 149-2, labeled “Stocks”;        -   Icon 436 for map module 154, labeled “Map”;        -   Icon 438 for weather widget 149-1, labeled “Weather”;        -   Icon 440 for alarm clock widget 169-6, labeled “Clock”;        -   Icon 442 for workout support module 142, labeled “Workout            Support”;        -   Icon 444 for notes module 153, labeled “Notes”; and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely examples. For example, in some embodiments, icon 422 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Device 300also, optionally, includes one or more contact intensity sensors (e.g.,one or more of sensors 359) for detecting intensity of contacts ontouch-sensitive surface 451 and/or one or more tactile output generators359 for generating tactile outputs for a user of device 300.

FIG. 4B illustrates an example user interface on a device (e.g., device300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet ortouchpad 355, FIG. 3) that is separate from the display 450. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 inFIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to aprimary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). Inaccordance with these embodiments, the device detects contacts (e.g.,460 and 462 in FIG. 4B) with the touch-sensitive surface 451 atlocations that correspond to respective locations on the display (e.g.,in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In thisway, user inputs (e.g., contacts 460 and 462, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 451 in FIG.4B) are used by the device to manipulate the user interface on thedisplay (e.g., 450 in FIG. 4B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

Multiple Device Environments

FIG. 5 illustrates an environment 500 including multiple electronicdevices such as those described above. The environment 500 includes asmartphone 501, a tablet 502, a media player 503 (connected to atelevision display), and a second smartphone 504. Although the exampleenvironment 500 of FIG. 5 includes four devices, it is to be appreciatedthat other environments can include other numbers of devices and otherdevices, such as a laptop, desktop computer, or a smartwatch. A user 599with limited motor skills, such as those with certain finger or handimpairments, may find interacting with the smartphone 501 (and otherdevices) via the touch-sensitive surface difficult, if not impossible.Thus, the smartphone 501 can be configured to operate in anaccessibility mode in which input from a switch device 510 is used tonavigate the user interface.

The switch device 510 generates a binary input stream including binaryinputs that are communicated to the smartphone 501. The switch device510 can include, for example, a switch that produces an “on” input whenthe switch is pressed and an “off” input when the switch is not pressed.The switch device 510 can include, as another example, a camera thatproduces an “on” input when the user turns his/her head to the left andan “off” input when the camera does not detect this motion. The binaryinput stream can be, for example, a voltage wave form that has a firstvalue (e.g., 5 V) to indicate an “on” input and a second value (e.g., 0V) to indicate an “off” input.

The switch device 510 can generate multiple binary input streams thatare communicated to the smartphone 501. The switch device 510 caninclude, for example, a first switch and a second switch. The firstswitch produces a first “on” input when the first switch is pressed anda first “off” input when the first switch is not pressed. Similarly, thesecond switch produces a second “on” input when the second switch ispressed and a second “off” input when the second switch is not pressed.The first “on” input and the second “on” input can have differenteffects in operating the smartphone 501. As another example, the switchdevice 510 can include a camera that produces a first “on” input whenthe user turns his/her head to the left and a second “on” input when theuser turns his/her head to the right.

A variety of devices for people of limited mobility can be used togenerate switch inputs, including a device that detects when air inblown into a straw or when the person blinks.

In the accessibility mode, the smartphone 501 interprets the input fromthe switch device 510 to navigate the user interface. In someimplementation, the user interface includes a selection indicator thatsequentially highlights interface objects. In some embodiments, when theselection indicator is highlighting a first interface object and aselect switch input (e.g., a first “on” input) is received, a menu forinteracting with the interface object is displayed. In some embodiments,when the selection indicator is highlighting a first interface object,the selection indicator moves to a second interface object automaticallyafter a time, e.g. a scanning period. In some embodiments, when theselection indicator is highlighting a first interface object, theselection indicator moves to a second interface object upon receiving anext switch input (e.g., a second “on” input).

The switch device 510 can be connected to the smartphone 501 via a wiredor wireless connection. However, a user 599 with limited motor skillsmay find it difficult, if not impossible, to disconnect the switchdevice 510 from the smartphone 501 and connect the switch device 510 toanother device (e.g., the tablet 502) to control the other device usingthe switch device 510 in the accessibility mode. Accordingly, describedbelow are various method, devices, and user interfaces for allowing auser to control multiple devices in an accessibility mode using a singleswitch device 510.

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as the smartphone 501, tablet 502, or media player 503 ofFIG. 5.

FIGS. 6A-6BD illustrate example user interfaces for controlling multipledevices in an accessibility mode in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIGS. 7A-7G.

FIG. 6A illustrates an environment 600 including the smartphone 501,coupled to a switch device 690 with a first switch 691 and a secondswitch 692, and the tablet 502. The switch device 690 generate multiplebinary input streams that are communicated to the smartphone 501. Theswitch device 690 includes, for example, a first switch 691 and a secondswitch 692. The first switch 691 produces a first “on” input when thefirst switch is pressed and a first “off” input when the first switch isnot pressed. Similarly, the second switch produces a second “on” inputwhen the second switch is pressed and a second “off” input when thesecond switch is not pressed. As described below, the first “on” inputand the second “on” input can have different effects in operating thesmartphone 501. Accessibility switch devices are frequently used bypeople who have difficulty operating a standard input mechanism for acomputer (e.g., mouse, keyboard, trackpad, touch-sensitive display).Accessibility switch devices come in a variety of differentconfigurations that are tailored to users with different accessibilityneeds (e.g., switches that can be activated via foot inputs, via handinputs, via breathing, via eye tracking, via head movement, etc.). Whileaccessibility switch devices are designed to be easier to activate forusers with different accessibility needs, they rely on software tointelligently provide binary decisions to navigate through the userinterface instead of the more complex inputs that are possible withstandard input mechanisms. The smartphone 501 displays a first userinterface 610 including a plurality of interface objects 611A-611G on adisplay of the smartphone 501. The tablet 502 displays a second userinterface 620 including a plurality of interface objects 621A-621J on adisplay of the tablet 502. Although substantially rectangular interfaceobjects are illustrated in FIGS. 6A-6BD, the interface objects can becircular, irregular, or any other shape.

The first user interface 610 includes a selection indicator 695highlighting a first interface object 611A. Although FIGS. 6A-6BDillustrate the selection indicator 695 as surrounding the firstinterface object 611A, in various implementations, the selectionindicator 695 highlights the interface object 611A in other ways. Forexample, in various implementations, the selection indicator 695surrounds the interface object, is displayed over the interface object,changes a visual characteristic of the interface object (e.g., abrightness, a contrast, or a color), points to a location of interfaceobject, or otherwise highlights the interface object.

FIG. 6A illustrates a switch device 690 coupled to the smartphone 501.In various implementations, the switch device 690 can be coupled to thesmartphone via a wired or wireless (e.g., Bluetooth™) connection. Theswitch device 690 includes a first switch 691 configured to provide aselect input and a second switch 692 configured to provide a next input.In some embodiments, the switch device 690 includes only the firstswitch 691 and the selection indicator 695 moves to a next interfaceobject automatically after a scanning period. As described furtherbelow, the first switch 691 and second switch 692 are configurable toprovide switch inputs besides the select input and the next input.Further, the scanning speed (e.g., the length of the scanning period) isalso configurable.

FIG. 6A illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6B illustrates the environment 600 of FIG. 6A in response todetecting the next input. In FIG. 6B, the selection indicator 695highlights a second interface object 611B.

FIG. 6B illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501.

FIG. 6C illustrates the environment 600 of FIG. 6B in response todetecting the select input. The user interface 610 includes a firstinteraction menu 631 including a plurality of interaction affordances.The interaction affordances include a tap affordance 631A for performinga tap operation associated with a tap of the interface object 611B. Theinteraction affordances include a scroll affordance 631B for performinga scroll operation (e.g., replacing the interface objects 611A-611G withother interface objects). The interaction affordances include a moreaffordance 631C for displaying a second interaction menu. In FIG. 6C,the tap affordance 631A is highlighted and the other interactionaffordances are not highlighted.

FIG. 6C illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6D illustrates the environment 600 of FIG. 6C in response todetecting the next input. In FIG. 6D, the scroll affordance 631B ishighlighted and the other interaction affordances are not highlighted.

FIG. 6D illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6E illustrates the environment 600 of FIG. 6D in response todetecting the next input. In FIG. 6E, the more affordance 631C ishighlighted and the other interaction affordances are not highlighted.

FIG. 6E illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501.

FIG. 6F illustrates the environment 600 of FIG. 6E in response todetecting the select input. In FIG. 6F, the first interaction menu 631is replaced with a second interaction menu 632. The second interactionmenu 632 includes a plurality of interaction affordances. Theinteraction affordances include a gestures affordance 632A fordisplaying a gestures menu. The gestures menu can include a plurality ofgesture affordances for performing operations associated with performingtouch gestures at a location of the interface object 611B. Theinteraction affordances include a device affordance 632B for display adevice menu. The device menu can include a plurality of deviceaffordances for performing operations on the device, such as returningto a home screen, entering a settings screen, changing a volume of thedevice, or powering down the device. The interaction affordances includea transfer control affordance 632C for controlling other devices usingthe switch device 690 (as described in detail below). The interactionaffordances include a back affordance 632D for exiting the secondinterface menu (and returning to the state of FIG. 6B). In FIG. 6F, thegestures affordance 632A is highlighted and the other interactionaffordances are not highlighted.

FIG. 6F illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6G illustrates the environment 600 of FIG. 6F in response todetecting the next input. In FIG. 6G, the device affordance 632B ishighlighted and the other interaction affordances are not highlighted.

FIG. 6G illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6H illustrates the environment 600 of FIG. 6G in response todetecting the next input. In FIG. 6H, the transfer control affordance632D is highlighted and the other interaction affordances are nothighlighted.

FIG. 6H illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501.

FIG. 6I illustrates the environment 600 of FIG. 6H in response todetecting the select input. In FIG. 6I, the second interaction menu 632is replaced with a device select menu 633 including a plurality ofdevice select affordances. In response to detecting the select inputwhile the transfer control affordance 632D is highlighted, thesmartphone 501 scans the environment to detect the presence of othernearby devices. For example, the smartphone 501 can be associated with auser account and can access a list of other devices associated with theuser account. For each other device on the list, the smartphone 501 candetermine whether the other device is nearby based on a proximitysensor, GPS location information, network connectivity (e.g., connectedto the same WLAN), or other information. In some embodiments, the deviceselect affordances include a device select affordance for each detectednearby device.

In FIG. 6I, the device select affordances include a media player selectaffordance 633A for selecting a media player 503 of the environment 600.The device select affordances include a tablet select affordance 633Bfor selecting the tablet 502 of the environment 600. The device selectaffordances include a phone select affordance for selecting a smartphone504 of the environment 600. The device select menu 633 also includes aback affordance 633D for exiting the device select menu (and returningto the state of FIG. 6B or, alternatively, to the state of FIG. 6H). InFIG. 6I, the media player select affordance 633A is highlighted and theother affordances of the device select menu 633 are not highlighted.

FIG. 6I illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6J illustrates the environment 600 of FIG. 6I in response todetecting the next input. In FIG. 6J, the tablet select affordance 633Bis highlighted and the other affordances of the device select menu 633are not highlighted.

FIG. 6J illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501.

FIG. 6K illustrates the environment 600 of FIG. 6J in response todetecting the select input. In FIG. 6K, the device select menu 633 isreplaced with a transfer control confirmation menu 634. The transfercontrol confirmation menu 634 include a confirmation affordance 634A fortransferring control to the selected device and a back affordance 634Bfor exiting the transfer control confirmation menu 634 (and returning tothe state of FIG. 6B or, alternatively, to the state of FIG. 6H or 6J).

The first user interface 610 includes a first transfer confirmationnotification 641A indicating that selection of the confirmationaffordance 634A will transfer control to the selected device (e.g., thetablet 502). The second user interface 620 includes a second transferconfirmation notification 641B indicating that selection of theconfirmation affordance 634A will transfer control to the device uponwhich the second transfer confirmation notification 641B is displayed(e.g., the tablet 502).

Thus, if a user mistakenly selects an unintended device (e.g., a devicethat is not visible or nearby), the first transfer confirmationnotification 641A and second transfer confirmation notification 641Bprovide an indication that a mistake has been made.

FIG. 6K illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501.

FIG. 6L illustrates the environment 600 of FIG. 6K in response todetecting the select input. In FIG. 6L, the selection indicator 695 ispart of the second user interface 620 of the tablet 501, highlighting afirst interface object 621A. The first user interface 610 includes afirst transferred control notification 642A indicating that the switchdevice 690 coupled to the smartphone 501 is interacting with the seconduser interface 620 of the tablet 502 (and not the first user interface610 of the smartphone 501). The second user interface 620 includes asecond transferred control notification 642B indicating that the seconduser interface 620 is being controlled by the switch device 690 coupledto the smartphone 501 (and not any other input device of the tablet 502or connected to the tablet 502). In some embodiments, the firsttransferred control notification 642A and/or the second transferredcontrol notification 642B persist as long as the second device is beingoperated based on input from the switch device 690.

In some implementations, switch inputs received from the switch deviceare received by the smartphone 501 and forwarded by the smartphone 501to the tablet 502. In some implementations, switch inputs received fromthe switch device are sent directly to the second device. Thus, in someimplementations, upon detecting the select input while highlighting ofthe confirmation affordance 634A, the smartphone 501 configures thetablet 502 to establish a connection with the switch device 690.

FIG. 6L illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6M illustrates the environment 600 of FIG. 6L in response todetecting the next input. In FIG. 6M, the selection indicator 695 hasmoved to highlight a second interface object 621B.

FIG. 6M illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6N illustrates the environment 600 of FIG. 6M in response todetecting the next input. In FIG. 6N, the selection indicator 695 hasmoved to highlight a third interface object 621C.

FIG. 6N illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6O illustrates the environment 600 of FIG. 6N in response todetecting the select input. The second user interface 620 includes thefirst interaction menu 631 displayed in association with the thirdinterface object 621C. The tap affordance 631A of the first interactionmenu 631 is highlighted and the other affordances of the firstinteraction menu 631 are not highlighted.

FIG. 6O illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6P illustrates the environment 600 of FIG. 6O in response todetecting the next input. In FIG. 6P, the scroll affordance 631B of thefirst interaction menu 631 is highlighted and the other affordances ofthe first interaction menu 631 are not highlighted.

FIG. 6P illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6Q illustrates the environment 600 of FIG. 6P in response todetecting the next input. In FIG. 6Q, the more affordance 631C of thefirst interaction menu 631 is highlighted and the other affordances ofthe first interaction menu 631 are not highlighted.

FIG. 6Q illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6R illustrates the environment 600 of FIG. 6Q in response todetecting the select input. In FIG. 6R, the first interaction menu 631is replaced with a transferred control second interaction menu 635. Thetransferred control second interaction menu 635 differs from the secondinteraction menu 632 (e.g., as shown in FIG. 6F) in that it includes areturn affordance 632E for returning control to the smartphone 501. InFIG. 6R, the gestures affordance 632A is highlighted and the otheraffordances of the transferred control second interaction menu 635 arenot highlighted.

FIG. 6R illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6S illustrates the environment 600 of FIG. 6R in response todetecting the next input. In FIG. 6S, the device affordance 632A ishighlighted and the other affordances of the transferred control secondinteraction menu 635 are not highlighted.

FIG. 6S illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6T illustrates the environment 600 of FIG. 6S in response todetecting the next input. In FIG. 6T, the return affordance 632E ishighlighted and the other affordances of the transferred control secondinteraction menu 635 are not highlighted.

FIG. 6T illustrates that the first switch 691 is activated, resulting ina next input detected by the smartphone 501 (and forwarded to the tablet502).

FIG. 6U illustrates the environment of FIG. 6T in response to detectingthe select input. In FIG. 6U, control is returned to the smartphone 501and the environment is in the same state as in FIG. 6A. Thus, switchinputs received from the switch device 690 will affect the first userinterface 610 of the smartphone 501 (as shown, for example, in FIGS.6B-6K).

FIG. 6V, like FIG. 6T, illustrates the environment of FIG. 6S inresponse to detecting the next input. Unlike FIG. 6T, FIG. 6Villustrates that the second switch 692 is activated, resulting in a nextinput detected by the smartphone 501 (and forwarded to the tablet 502).

FIG. 6W illustrates the environment 600 of FIG. 6V in response todetecting the next input. In FIG. 6W, the transfer control affordance632C is highlighted and the other affordances of the transferred controlsecond interaction menu 635 are not highlighted.

FIG. 6W illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6X illustrates the environment 600 of FIG. 6W in response todetecting the select input. In FIG. 6X, the transferred control secondinteraction menu 635 is replaced with a transferred control deviceselect menu 636 including a plurality of device select affordances. Thetransferred control device select menu 636 differs from the deviceselect menu 633 (e.g., as shown in FIG. 6I) in that it includes asmartphone select affordance 633E for selecting the smartphone 501 anddoes not include a tablet affordance 633B for selecting the tablet 502.In FIG. 6X, the media player select affordance 633A is highlighted andthe other affordances of the transferred control device select menu 636are not highlighted.

FIG. 6X illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6Y illustrates the environment 600 of FIG. 6X in response todetecting the select input. In FIG. 6Y, the transferred control deviceselect menu 636 is replaced with the transfer control confirmation menu634. As described above with respect to FIG. 6K, the transfer controlconfirmation menu 634 include a confirmation affordance 634A(highlighted in FIG. 6Y) for transferring control to the selected deviceand a back affordance 634B (not highlighted in FIG. 6Y) for exiting thetransfer control confirmation menu 634.

The second user interface 620 includes the first transfer confirmationnotification 641A indicating that selection of the confirmationaffordance 634A will transfer control to the selected device (e.g., themedia player 503). The user interface of the media player can alsoinclude the second transfer confirmation notification 641B indicatingthat selection of the confirmation affordance 634A will transfer controlto the device upon which the second transfer confirmation notification641B is displayed (e.g., the media player 503).

FIG. 6Y illustrates that the first switch 691 is activated, resulting ina select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6Z illustrates the environment 600 of FIG. 6Y in response todetecting the select input. In FIG. 6Z, the selection indicator 695 ismoved to a third user interface 660 of the media player 503, displayedon a display 503A coupled to the media player 503. The third userinterface 660 includes a plurality of interface objects 661A-661E withthe selection indicator 695 highlighting a first interface object 661A.

The first user interface 610 of the smartphone 501 includes the firsttransferred control notification 642A indicating that the switch device690 coupled to the smartphone 501 is interacting with the third userinterface 660 of the media player 503 (and not the first user interface610 of the smartphone 501). The third user interface 660 of the mediaplayer 503 includes the second transferred control notification 642Bindicating that the third user interface 660 is being controlled by theswitch device 690 coupled to the smartphone 501 (and not any other inputdevice of the media play 503 or connected to the media player 503).

FIG. 6Z illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501 (and forwarded to themedia player 503).

FIG. 6AA illustrates the environment 600 of FIG. 6Z in response todetecting the next input. The third user interface 660 includes theselection indicator 695 moved from the first interface object 661A tothe second interface object 661B.

FIG. 6AA illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501 (and forwarded to themedia player 503).

FIG. 6AB illustrates the environment 600 of FIG. 6AA in response todetecting the select input. The third user interface 660 includes amedia interaction menu 637 including a plurality of media interactionaffordances. The media interaction affordances include a selectaffordance 637A for selecting the highlighted interface object. Themedia interaction affordances include a scroll affordance 637B forscrolling the third user interface 660. The media interactionaffordances include a remote affordance 637C for displaying a virtualremote including a plurality of remote affordances for interacting withthe third user interface 660. The media interaction affordances includea more affordance 637D for showing a second media interaction menu withother media interaction affordances.

FIG. 6AC, like FIG. 6N, illustrates the environment of FIG. 6M inresponse to detecting the next input. Unlike FIG. 6N, FIG. 6Villustrates that the first switch 691 and second switch 692 areactivated, resulting in a select input and a next input detected by thesmartphone 501 (and forwarded to the tablet 502). Such a combined inputcan be configured, as described further below, as an escape input toreturn control to the smartphone 601.

FIG. 6AD illustrates the environment of FIG. 6AC in response todetecting the escape input. In FIG. 6AD, control is returned to thesmartphone 501 and the environment is in the same state as in FIG. 6A.Thus, switch inputs received from the switch device 690 will affect thefirst user interface 610 of the smartphone 501 (as shown, for example,in FIGS. 6B-6K).

Thus, control can be returned to the smartphone 501 in a number of ways.Control can be returned to the smartphone 501 by selecting a returnaffordance 632A of a transferred control interaction menu 635, as shownin FIG. 6T. Control can be returned to the smartphone 501 by selectingthe smartphone select affordance 633E of the transferred control deviceselect menu 636, as shown in FIG. 6X. Control can be returned to thesmartphone 501 by inputting the escape input, as shown in FIG. 6AC. Theescape input can be particularly useful for users with limited mobilitywho cannot easily find a device that is not behaving correctly (andunable to effect the other two forms of returning control) and reset itor otherwise correct a problem with the device. Further, if the usermistakenly transfers control to a second device that is not visible,control can be returned to the first device without interacting with thesecond device.

FIG. 6AE illustrates the environment 600 of FIG. 6AC in response to analert being generated by the smartphone 501 (without the escape inputbeing provided or detected), e.g., while switch inputs from the switchdevice 690 control the second user interface 620 of the tablet 502.

The first user interface 610 displays an alert user interface 615 basedon the alert. In FIG. 6AE, the alert is generated in response to areceived phone call. In various implementations, the alert can be, forexample, a text message, a timer expiration, a clock alarm, or an eventreminder. The alert user interface 615 includes alert information 616regarding the alert and one or more affordances for responding to thealert. In FIG. 6AE, the affordances for responding to the alert includea slide affordance 617 for answering the phone call.

The second user interface 610 includes an alert response menu 638 with aplurality of alert response affordances. The alert response affordancesinclude a dismiss affordance 638A for dismissing the alert response menu638 without any action taken on the smartphone 501. The alert responseaffordances include a return affordance 638B for returning control tothe smartphone 501. The alert response affordances include an answeraffordance 638C for answering the phone call. The alert responseaffordances include an ignore affordance 638D for ignoring the phonecall. In FIG. 6AE, the dismiss affordance 638A is highlighted and theother affordances of the alert response menu 638 are not highlighted. Invarious implementations, the alert response affordances can includeaffordances for responding to a text message, snoozing a clock alarm, ordisplaying information regarding an event.

FIG. 6AE illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6AF illustrates the environment 600 of FIG. 6AE in response todetecting the select input. In FIG. 6AF, the alert response menu 638 isno longer displayed on the second user interface 620 and switch inputscontinue to control the second user interface 620. On the first userinterface 610, the alert user interface 615 is displayed unchanged andno action is taken with respect to the phone call.

FIG. 6AG, like FIG. 6AE, illustrates the environment of FIG. 6AC inresponse to the alert being generated by the smartphone. Unlike FIG.6AE, FIG. 6AG illustrates that the second switch 692 is activated,resulting in a next input detected by the smartphone 501 (and forwardedto the tablet 502).

FIG. 6AH illustrates the environment of FIG. 6AG in response todetecting the next input. In FIG. 6AH, the return affordance 638B ishighlighted and the other affordances of the alert response menu 638 arenot highlighted.

FIG. 6AH illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6AI illustrates the environment of FIG. 6AH in response todetecting the select input. In FIG. 6AI, the first transferred controlnotification 642A and second transferred control notification 642B arenot displayed indicating that control has returned to the smartphone501. The selection indicator 695 highlights the slide affordance 617 andswitch inputs from the switch device can be detected to operate thesmartphone 501, e.g., to answer the phone call.

FIG. 6AJ, like FIG. 6AH, illustrates the environment of FIG. 6AG inresponse to detecting the next input. Unlike FIG. 6AH, FIG. 6AJillustrates that the second switch 692 is activated, resulting in a nextinput detected by the smartphone 501 (and forwarded to the tablet 502).

FIG. 6AK illustrates the environment 600 of FIG. 6AJ in response todetecting the next input. In FIG. 6AK, the answer affordance 638C ishighlighted and the other affordances of the alert response menu 638 arenot highlighted.

FIG. 6AK illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6AL illustrates the environment 600 of FIG. 6AK in response todetecting the select input. In response to detecting the select input,the smartphone 501 answers the phone call, but the switch inputs arestill forwarded to the tablet 502. On the first user interface 610, ananswered call user interface 615A is displayed including informationregarding the phone call and a number of call affordances. On the seconduser interface 620, an answered call menu 639 is displayed including aplurality of call affordances. The call affordances include a muteaffordance 639A for muting the answered phone call. The call affordancesinclude a keypad affordance 639B for displaying a keypad. The callaffordances include a hang-up affordance 639C for ending the answeredphone call. In FIG. 6AL, the mute affordance 639A is highlighted and theother affordances of the answered call menu 639 are not highlighted.

FIG. 6AM, like FIG. 6AK, illustrates the environment 600 of FIG. 6AJ inresponse to detecting the next input. Unlike FIG. 6AK, FIG. 6AMillustrates that the second switch 692 is activated, resulting in a nextinput detected by the smartphone 501 (and forwarded to the tablet 502).

FIG. 6AN illustrates the environment 600 of FIG. 6AM in response todetecting the next input. In FIG. 6AM, the ignore affordance 638D ishighlighted and the other affordances of the alert response menu 638 arenot highlighted.

FIG. 6AN illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501 (and forwarded to thetablet 502).

FIG. 6AO illustrates the environment 600 of FIG. 6AN in response todetecting the select input. In response to the select input, thesmartphone 501 ignores the phone call and the environment 600 isreturned to the state of FIG. 6AC (without the escape input beingprovided or detected), e.g., while switch inputs from the switch device690 control the second user interface 620 of the tablet 502.

FIG. 6AP, like FIG. 6G, illustrates the environment 600 of FIG. 6F inresponse to detecting the next input. In FIG. 6G, the device affordance632B is highlighted and the other interaction affordances are nothighlighted. Unlike FIG. 6G, FIG. 6AP illustrates that the first switch691 is activated, resulting in a select input detected by the smartphone501.

FIG. 6AQ illustrates the environment 600 of FIG. 6AP in response todetecting the response input. In FIG. 6AQ, the second interaction menu632 is replaced with a device menu 639 including a plurality of devicemenu affordances. The device menu affordances include a home affordance639A for performing a home operation (e.g., returning to a home userinterface). The device menu affordances include a settings affordance639B for accessing a settings user interface. The device menuaffordances include a lock affordance 639C for locking the smartphone501. The device menu affordances include a back affordance 639D forexiting the device menu 639 (and returning to the state of FIG. 6B). InFIG. 6AQ, the home affordance 639A is highlighted and the otheraffordances of the device menu 639 are not highlighted.

FIG. 6AQ illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6AR illustrates the environment 600 of FIG. 6AQ in response todetecting the next input. In FIG. 6AR, the settings affordance 639B ishighlighted and the other affordances of the device menu 639 are nothighlighted.

FIG. 6AR illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6AS illustrates the environment 600 of FIG. 6AR in response todetecting the select input. In FIG. 6AS, the first user interface 610displays a settings user interface 671. The settings user interface 671includes a plurality of settings affordances for changing varioussettings of the smartphone 501. The settings affordances include aconnectivity settings affordance 671A for changing connectivity settingsof the smartphone 501, e.g., WLAN network connections, turning on andoff an airplane mode, configuring the smartphone 501 as a hotspot, etc.The settings affordances include an accessibility settings affordance671B for changing accessibility settings of the smartphone 501, asdescribed further below. The settings affordances include a soundsettings affordance 671C for changing sound settings of the smartphone501, such as a maximum volume, ringtones, etc. The settings affordancesinclude a display settings affordance 671D for changing display settingsof the smartphone 501, such as a brightness, a text size, etc. Thesettings affordances include an applications settings affordance 671Efor changing settings of various applications of the smartphone 501. InFIG. 6AS, the selection indicator 695 highlights the connectivitysettings affordance 671A.

FIG. 6AS illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6AT illustrates the environment 600 of FIG. 6AS in response todetecting the next input. In FIG. 6AT, the selection indictor 695highlights the accessibility settings affordance 671B.

FIG. 6AT illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6AU illustrates the environment 600 of FIG. 6AT in response todetecting the select input. In FIG. 6AU, the first user interface 610displays an accessibility settings user interface 672 including aplurality of accessibility settings affordances. The accessibilitysettings affordances include an accessibility mode toggle affordance672A for switching in and out of the accessibility mode. Theaccessibility settings affordances include a switches settingsaffordance 672B for adding switches and configuring user interfaceresponses to the switches, as described further below. The accessibilitysettings affordances include a scanning speed affordance 672C forchanging a scanning speed of the selection indicator 695. Theaccessibility settings affordances include a highlight color affordance672D for changing a color of the selection indicator 695. Theaccessibility settings affordance include an escape action affordance672E for changing the action required to form the escape input. In FIG.6AU, the selection indicator 695 highlights the accessibility modetoggle affordance 672A. The accessibility settings user interface 672includes a settings affordance 672X for returning to the settings userinterface 671.

FIG. 6AU illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6AV illustrates the environment 600 of FIG. 6AU in response todetecting the next input. In FIG. 6AV, the selection indicator 695highlights the switches settings affordance 672B.

FIG. 6AV illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6AW illustrates the environment 600 of FIG. 6AV in response todetecting the select input. In FIG. 6AW, the first user interface 610displays a switches settings user interface 673. The switches settingsuser interface 673 includes a plurality of switches settings affordancesfor changing switch settings of the accessibility mode of the smartphone501.

The switches settings affordances include a switch action affordance673A for changing an action taken by the first user interface 610 inresponse to a switch input from the first switch 691. As described withrespect to the figures above, the switch input from the first switch 691is interpreted by the smartphone 501 as a select input. In variousimplementations, the switch input can be interpreted as a stop/startscanning input that stops or starts scanning of the selection indicator695, a next input that moves the selection indicator 695 to a nextinterface object, a previous input that moves the selection indicator695 to a previous interface object, a tap input that is interpreted ason tap on the touchscreen at the location of the selection indicator695, a volume input that increases or decreases the volume of thesmartphone 501, or as another input.

The switches settings affordances include an other device switch actionaffordance 673B for changing an action taken by the second userinterface 620 (and/or third user interface 660) in response to a switchinput from the first switch 691. In some implementations, the actiontaken by the second user interface 620 is the same as the action takenby the first user interface 620 (as shown in FIG. 6AW). However, in someimplementations, the action taken by the second user interface 620 isdifferent from the action taken by the first user interface 610. Forexample, a user can configure the action taken by the first userinterface 610 in response to a switch input from the second switch 692to be a next action (e.g., moving the selection indicator 695 to a nextinterface object), but configure the action taken by the second userinterface 620 in response to a switch input from the second switch 692to be a scroll action (e.g., scrolling a set of interface objects). Auser may wish to do so when the first device is a smartphone and thesecond device is a media player in which scrolling is an often performedtask.

The switches settings affordances include a backup other device switchaction affordance 673C for changing a backup action taken by the seconduser interface 620 in response to a switch input from the first switch691 in circumstances in which the second user interface 620 does notsupport the primary action.

The switches settings affordances include a full screen actionaffordance 673C for changing an action taken by the first user interface610 in response to a touch anywhere on the touchscreen of the smartphone501. Thus, the touchscreen of the smartphone 501 can be configured as aswitch device as an alternative to or in addition to the switch device690.

The switches settings affordances include an add switch deviceaffordance 673E for configuring the smartphone to accept switch inputsfrom other switch devices (not shown).

The switches settings user interface includes an accessibility settingsaffordance 673X for returning to the accessibility settings userinterface 672. In FIG. 6AW, the selection indicator 695 highlights theaccessibility settings affordance 673X.

FIG. 6AW illustrates that the first switch 691 is activated, resultingin a select input detect by the smartphone 501.

FIG. 6AX illustrates the environment 600 of FIG. 6AW in response todetecting the select input. In FIG. 6AX, the first user interface 610displays the accessibility settings user interface 672 with theselection indicator 695 highlighting the switches settings affordance672B.

FIG. 6AX illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6AY illustrates the environment 600 of FIG. 6AX in response todetecting the next input. In FIG. 6AY, the selection indicator 695 hasmoved to highlight the scanning speed affordance 672C.

FIG. 6AY illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6AZ illustrates the environment 600 of FIG. 6AY in response todetecting the select input. In FIG. 6AZ, the first user interface 610displays a scanning speed user interface 674 including a plurality ofscanning speed setting affordances. The scanning speed settingaffordances include a primary scanning speed setting affordance 674A forchanging the scanning speed of the selection indicator 695 on thesmartphone 501. In FIG. 6AZ, the scanning speed on the smartphone 501 isset to manual. In various implementations, the scanning speed can be setto one of a set of speeds (e.g., slow, medium, and fast) or can be setto a specific scanning period (e.g., half a second, 1 second, or 2seconds).

The scanning speed setting affordances include device scanning speedsetting affordances 674B-674D for changing the scanning speed of theselection indicator on other specific devices, such as the tablet 502,the second smartphone 504, or the media player 503. In FIG. 6AZ, thetablet scanning speed affordance 674B indicates that the scanning speedon the tablet 502 is the same as the scanning speed on the smartphone501. Thus, the scanning speed on the tablet 502 is also set to manual.In circumstances when the scanning speed is set to one of a set ofspeeds (e.g., medium), the device scanning speed affordances 674B-674Dcan also be set to a “same” setting in which the scanning speed on thedevice is based on, but not necessarily identical to, the scanning speedon the smartphone 501. Thus, although both devices may have a scanningspeed setting of “medium”, the scanning period of the selectionindicator 695 may have different values. In some circumstances, thescanning periods are identical, e.g., when the scanning speed setting isset to specify a specific scanning period.

The scanning speed set affordances include a catchall scanning speedaffordance 674E for changing a scanning speed on other devices notdisplayed in the scanning speed user interface 674.

The scanning speed user interface 674 includes an accessibility settingsaffordance 674X for returning to the accessibility settings userinterface 672. In FIG. 6AZ, the selection indicator 695 highlights theaccessibility settings affordance 674X.

FIG. 6AZ illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6BA illustrates the environment 600 of FIG. 6AZ in response todetecting the select input. In FIG. 6BA, the first user interface 610displays the accessibility settings user interface 672 with theselection indicator 695 highlighting the scanning speed affordance 672C.

FIG. 6BA illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6BB illustrates the environment 600 of FIG. 6BA in response todetecting the next input. In FIG. 6BB, the selection indicator 695 hasmoved to highlight the highlight color affordance 672D.

FIG. 6BB illustrates that the second switch 692 is activated, resultingin a next input detected by the smartphone 501.

FIG. 6BC illustrates the environment 600 of FIG. 6BB in response todetecting the next input. In FIG. 6BC, the selection indicator 695 hasmoved to highlight the escape action affordance 672E.

FIG. 6BC illustrates that the first switch 691 is activated, resultingin a select input detected by the smartphone 501.

FIG. 6BD illustrates the environment 600 of FIG. 6BC in response todetecting the select input. In FIG. 6BD, the first user interface 610displays an escape action user interface 675 including a plurality ofescape action setting affordances. The escape action setting affordancesinclude a hold primary switch affordance 675A for setting the escapeaction to holding the first switch 691 for at least a threshold amountof time (e.g., 10 seconds, 30 seconds, 1 minute, etc.) The escape actionsetting affordances include a multiple switches affordance 675B forsetting the escape action to pressing multiple switches simultaneously(e.g., the first switch 691 and the second switch 692). In FIG. 6BD, themultiple switches affordance 675B is bolded, indicating that the escapeaction is to press multiple switches as shown in FIG. 6AC. The escapeaction setting affordances include a multiple clicks affordance 675C forsetting the escape action to at least a threshold number in switchinputs in a time period (e.g., 20 switch inputs in 10 seconds). Theescape action setting affordances include a coded sequence affordance675C for setting the escape action to a coded sequence (e.g., SOS inMorse code). The escape action setting affordances include a customaction affordance 675E for setting the escape action to a custom action.

The escape action user interface includes an accessibility settingsaffordance 675X for returning to the accessibility settings userinterface 672. In FIG. 6BD, the selection indicator 695 highlights theaccessibility settings affordance 675X.

FIGS. 7A-7G illustrate a flow diagram of a method 700 of controllingmultiple devices in an accessibility mode in accordance with someembodiments. The method 700 is performed at an electronic device (e.g.,the portable multifunction device 100 in FIG. 1A, the device 300 in FIG.3, or any of the device 501-504 of FIG. 5) with one or more processors,non-transitory memory, and a display. In some embodiments, the displayis a touch-screen display and a touch-sensitive surface is on orintegrated with the display. In some embodiments, the display isseparate from the touch-sensitive surface. Some operations in method 700are, optionally, combined and/or the order of some operations is,optionally, changed.

As described below, the method 700 provides an intuitive way to controlmultiple devices in an accessibility mode. The method reduces thecognitive burden on a user when controlling multiple devices in anaccessibility mode, thereby creating a more efficient human-machineinterface. For battery-operated electronic devices, enabling a user tocontrol multiple devices in an accessibility mode faster and moreefficiently conserves power and increases the time between batterycharges.

The first device displays (702) a device control transfer affordancewhile operating the first device based on user input from an inputdevice that is in communication with the first device. For example, inFIG. 6K, the first device (e.g., the smartphone 501) displays aconfirmation affordance 634A that, when selected, transfers control fromthe first device to the second device (e.g., the tablet 502). In someembodiments, the device control transfer affordance is implemented asthe tablet affordance 633B of FIG. 6J and control is transferred with aconfirmation. In some embodiments, the device control transferaffordance is implemented as the transfer control affordance 632C ofFIG. 6H and control is transferred to a preselected second devicewithout a confirmation.

In some embodiments, operating the first device based on the user inputfrom the input device includes operating (704) the first device in anaccessibility mode of operation. For example, in FIG. 6AU, theaccessibility mode toggle affordance 672A indicates that anaccessibility mode is active throughout FIGS. 6A-6BD. In someembodiments, the accessibility mode of operation is a switch controlmode of operation where switch inputs are used to select and/or cyclethrough selection options.

In some embodiments, user input from the input device includes (706)switch inputs. As described above, switch inputs can be generates asportions of a binary input stream having, at each of a plurality oftimes, one of two values.

In some embodiments, at least one of the switch inputs is generated(708) by a switch device including one or more switches and designed foruse by users who are unable to use the standard input device(s) for thefirst device (e.g., a touchscreen). For example, in FIG. 6A, the switchdevice 690 includes a first switch 691 and a second switch 692.

In some embodiments, at least one of the switch inputs is generated(710) by an input device of the first device. For example, at least oneof the switch inputs can be generated (712) by a touchscreen of thefirst device. As another example, at least one of the switch inputs canbe generated (714) by a camera of the first device. For example, in FIG.6AW, the switches settings user interface 673 allows a user to set thefull area of the touchscreen of the first device as a switch device togenerate switch inputs or set a camera of the first device as a switchdevice that generates a first switch input when a left head turn isdetected and a second switch input when a right head turn is detected.

Thus, in some embodiments, the input device is integrated into the firstdevice, e.g., as a touchscreen, a home button, a volume up/down button,etc.). In some embodiments, the input device is separate from the firstdevice (e.g., as a dedicated switch device). In some embodiments, thefirst device includes one or more includes one or more integrated inputdevices that do not need to be used to control the device when aseparate input device is being used to control the first device. In someembodiments, the input device is wirelessly paired to the first device.In some embodiments, the input device is connected to the first devicewith a wire or other physical connection used for transferring data suchas input information from the input device to the first device.

In some embodiments, displaying the device control transfer affordanceincludes displaying (716), on the display, a scan affordance whileoperating the first device based on the user input from the inputdevice. For example, in FIG. 6H, the first device displays a transfercontrol affordance 632C. In some embodiments, displaying the devicecontrol transfer affordance include receiving (718) a scan user inputfrom the input device selecting the scan affordance. For example, inFIG. 6H, the first switch 691 is activated while the transfer controlaffordance 632C is highlighted. In some embodiments, displaying thedevice control transfer affordance includes displaying, on the display,in response to receiving the scan user input, one or more device selectaffordances while operating the first device, the one or more deviceselect affordances including a second device affordance associated withthe second device. For example, in FIG. 6I, the first device displays adevice select menu 633 including a plurality of device selectaffordances, the plurality of device select affordances including atablet select affordance 633B.

In some embodiments, displaying the device control transfer affordanceincludes receiving (722) a device select user input from the inputdevice selecting the second device affordance. For example, in FIG. 6J,the first switch 691 is activated while the tablet select affordance633C is highlighted. In some embodiments, displaying the device controltransfer affordance is performed in response to receiving the deviceselect user input for the input device selecting the second deviceaffordance.

In some embodiments, displaying the device control transfer affordanceincludes displaying (724), on the display of the first device, a firsttransfer confirmation notification indicating that the input device willbe used to operate the second device (and will not be used to operatethe first device) upon selection of the device control transferaffordance. Thus, if a user mistakenly selects an unintended device(e.g., a device that is not visible or nearby), the first transferconfirmation notification provide an indication that a mistake has beenmade preventing the user for transferring control to the unintendeddevice and, thus, requiring addition interaction to return control tothe first device and then to the intended device. Requiring lessinteraction conserves power and increases the time between batterycharges for battery-operated devices. Further, less interaction reduceswear-and-tear of the input device.

For example, in FIG. 6K, the first device displays a first transferconfirmation notification 641A indicating that control will betransferred to the second device.

In some embodiments, displaying the device control transfer affordanceincludes causing display (726), on the display of the second device, ofa second transfer confirmation notification indicating that the inputdevice (and not other input devices of the second device) will be usedto operate the second device upon selection, on the first device, of thedevice control transfer affordance. Thus, (like the first transferconfirmation notice) if a user mistakenly selects an unintended device(e.g., a device that is not visible or nearby), the second transferconfirmation notification provide an indication that a mistake has beenmade preventing the user for transferring control to the unintendeddevice and, thus, requiring addition interaction to return control tothe first device and then to the intended device. Requiring lessinteraction conserves power and increases the time between batterycharges for battery-operated devices. Further, less interaction reduceswear-and-tear of the input device. For example, in FIG. 6K, the seconddevice displays a second transfer confirmation notification indicatingthat control will be transferred to the device upon which it isdisplayed.

The first device receives (728) a device control transfer user inputfrom the input device selecting the device control transfer affordancethat is displayed on the display of the first device. For example, inFIG. 6K, the first switch 691 is activated while the confirmationaffordance 634A is highlighted.

The first device configures (730) the second device to be operated basedon user input from the input device and ceases to operate the firstdevice based on user input from the input device. Thus, a user can use asingle input device to control multiple devices without disconnectingthe input device from the first device and connecting the input deviceto the second device, which may be a time-consuming, if not impossible,process for persons of limited mobility. Using a single input device tocontrol multiple devices reduces costs for the user (as they need notpurchase multiple input devices). For example, in FIG. 6L, the firstdevice display a first transferred control notification 642A indicatingthat the second device is operated based on user input from the inputdevice.

In some embodiments, operating the second device based on the user inputfrom the input device includes operating (732) the second device in thesame accessibility mode of operation as the first device. For example,in FIG. 6L, the selection indicator 695 is moved from the first deviceto the second device and user input from the input device operates thesecond device, not the first device.

In some embodiments, configuring the second device to be operated basedon user input from the input device includes forwarding (734) inputsreceived from the input device to the second device. In someembodiments, configuring the second device to be operate based on userinput from the input device includes establishing (736) a connectionbetween the input device and the second device.

In some embodiments, the the first device displays (738), on the displayof the first device, a first transferred control notification indicatingthat operation of the second device (and not the first device) is basedon the user input from the input device. The first transferred controlnotification provides feedback to a user viewing the first device thatthe input device is not controlling the first device, preventing a userfrom attempting to operate the first device with the input device (andreducing frustration of the user in addition to wear-and-tear of theinput device). For example, in FIG. 6L, the first device displays afirst transferred control notification 642A indicating that the seconddevice is operated based on user input from the input device.

In some embodiments, the first device causes display (740), on thedisplay of the second device, of a second transferred controlnotification indicating that operation of the second device is based onthe user input from the input device (and not an input device of thesecond device). For example, in FIG. 6L, the second device displays asecond transferred control notification 642B indicating that the seconddevice is being controlled by the switch device 690 and not, forexample, the touchscreen of the tablet 502.

In some embodiments, the first device causes display (742), on thedisplay of the second device, of a device control return affordancewhile operating the second device based on user input from the inputdevice. By providing a device control return affordance, a user can justas efficiently transfer control from the second device to the firstdevice as the user can transfer control from the first device to thesecond device. Such an efficient user interface conserves power andincreases the time between battery charges for battery-operated devices.Further, an efficient user interface reduces wear-and-tear of the inputdevice. For example, in FIG. 6T, the second device displays a returnaffordance 632E. In some embodiments, the first device receives (744) adevice control return user input from the input device selecting thedevice control return affordance. For example, in FIG. 6T, the firstswitch 691 is activated while the return affordance 632E is highlighted.In some embodiments, the first device operates (746), in response toreceiving the device control return user input, the first device basedon user input from the input device and ceases to operate the seconddevice based on user input from the input device.

In some embodiments, the first device receives (748) an escape inputfrom the input device matching an escape action. The escape input can beparticularly useful for users with limited mobility who cannot easilyfind a device that is not behaving correctly (and unable to effect theother two forms of returning control) and reset it or otherwise correcta problem with the device. Further, if the user mistakenly transferscontrol to a second device that is not visible, control can be returnedto the first device without interacting with the second device. Forexample, in FIG. 6AC, both the first switch 691 and second switch 692are activated. In some implementations, the escape input is holding bothswitches for at least a threshold amount of time (e.g., 10 seconds). Insome embodiments, the first device operates (750), in response toreceiving the escape input, the first device based on user input fromthe input device and ceases to operate the second device based on userinput from the input device.

In some embodiments, the first device displays (752), on the display ofthe first device, an escape settings user interface including one ormore affordances for defining the escape action. For example, in FIG.6BD, the first device displays an escape action user interface 675including a plurality of escape action setting affordances.

In some embodiments, the first device displays (754), on the display ofthe first device, an accessibility settings user interface including oneor more affordances for changing one or more accessibility settings forthe second device. For example, in FIG. 6AU, the first device displaysan accessibility settings user interface 672 including a plurality ofaccessibility settings affordances.

In some embodiments, the accessibility settings user interface includes(756) one or more affordances for changing a scanning speed or highlightcolor of a selection indicator on the second device. For example, inFIG. 6AU, the first device display a scanning speed affordance 672C anda highlight color affordance 672D. In FIG. 6AZ, the first devicedisplays tablet scanning speed affordance 674B for changing a scanningspeed of the second device.

In some embodiments, the accessibility settings user interface includes(758) one or more affordances for changing a switch action of the seconddevice. For example, in FIG. 6AU, the first device displays a switchessettings affordance 672B. In FIG. 6AW, the first device displays another device switch action affordance 673B for changing a switch actionof the second device (and/or other devices).

In some embodiments, the accessibility settings user interface include(760) one or more affordances for changing a backup switch action of thesecond device. For example, in FIG. 6AU, the first device displays aswitches settings affordance 672B. In FIG. 6AW, the first devicedisplays a backup other device switch action affordance 673C forchanging a backup switch action of the second device (and/or otherdevices).

In some embodiments, one or more of the accessibility settings for thesecond device are (762) based on one or more accessibility settings offor the first device. Thus, a user need not duplicatively changesettings for multiple devices based on the user's preferences and/orabilities, requiring less interaction with the devices. Less interactionwith the user interface conserves power and increases the time betweenbattery charges for battery-operated devices. Further, less interactionwith the user interface reduces wear-and-tear of the input device. Forexample, in FIG. 6AW, the first device displays that the switch actionof the first switch for the first device and the switch action of thefirst switch for the second device are the same. As another example, inFIG. 6AZ, the first device displays that the scanning speed setting forthe first device and the scanning speed setting for the second deviceare the same.

In some embodiments, at least one of the accessibility settings for thesecond device is (764) different than a corresponding accessibilitysetting for the first device. For example, in FIG. 6AZ, the first devicedisplays that the scanning speed setting for the first device and thescanning speed setting for another device (e.g., the media player 503)are different.

In some embodiments, an accessibility setting for the second deviceindicating a switch action for a switch input is (766) different than anaccessibility setting for the first device indicating a switch actionfor the switch input. For example, in FIG. 6AW, the first devicedisplays that the switch action for a full screen touch on the firstdevice is different than the switch action on the second device.

In some embodiments, the first device generates (768) an alert at thefirst device while operating the second device based on the user inputfrom the input device. Thus, controlling the second device with theinput device does not decrease the functionality of first device andalerts (such as phone calls) can continue to be received by the user viathe first device. For example, in FIG. 6AE, the first device displays analert user interface 615 based on a received phone call. In otherembodiments, the alert can be, for example, a text message, a timerexpiration, a clock alarm, or an event reminder. In some embodiments,the first device displays (770), on the display of the second device, ofone or more alert response affordances. For example, in FIG. 6AE, thesecond device displays an alert response menu 638 with a plurality ofalert response affordances 638.

In some embodiments, the first device receives (772) a dismiss userinput selecting a dismiss affordance of the one or more alert responseaffordances. For example, in FIG. 6AE, the first switch 691 is activatedwhile the dismiss affordance 638A is highlighted. In some embodiments,the method 700 includes ceasing (774) display of the one or more alertresponse affordances in response to receiving the dismiss user input.For example, in FIG. 6AF, the second device ceases displaying the alertresponse menu 638.

In some embodiments, the first device receives (776) a return user inputselecting a return affordance of the one or more alert responseaffordances. For example, in FIG. 6AH, the first switch 691 is activatedwhile the return affordance 638B is highlighted. In some embodiments,the first device operates (778), in response to receiving the returnuser input, the first device based on user input from the input deviceand ceases to operate the second device based on user input from theinput device.

In some embodiments, the first device receives (780) a continued actionuser input selecting a continued action affordance of the one or morealert response affordances. For example, in FIG. 6AK, the first switch691 is activated while the answer affordance 638C is highlighted. Insome embodiments, the first device operates (782) the second devicebased on user input from the input device to respond to the alert. Forexample, in FIG. 6AL, the second device displays a menu for continuedaction with respect to the alert (e.g., further action in associationwith the answered phone call). In various implementations, the continuedaction affordance can include, for example, an affordance for respondingto a text message, snoozing a clock alarm, or displaying informationregarding an event.

In some embodiments, the first device receives (784) a quick action userinput selecting a quick action affordance of the one or more alertresponse affordances. Thus, a user can perform actions with respect toalerts received on the first device without returning control to thefirst device, reducing the amount of interaction with the userinterfaces of the first device and second device. Less interaction withthe user interface conserves power and increases the time betweenbattery charges for battery-operated devices. Further, less interactionwith the user interface reduces wear-and-tear of the input device. Forexample, in FIG. 6AN, the first switch 691 is activated while the ignoreaffordance 638D is highlighted. In some embodiments, the first devicedismisses (786) the alert at the first device and continuing to operatethe second device based on user input from the input device. Forexample, in FIG. 6AO, the first device ignores the phone call and theselection indicator 695 remains at the second device. In variousimplementations, the quick action affordance can include, for example,an affordance for dismissing a clock alarm or dismissing an eventreminder.

In some embodiments, the first device causes display (788), on a displayof the second device, of a third device control transfer affordancewhile operating the second device based on user input from the inputdevice. For example, in FIG. 6Y, the second device displays theconfirmation affordance 634A. In some embodiments, the first devicereceives (790) a third device control transfer user input from the inputdevice selecting the third device control transfer affordance. Forexample, in FIG. 6Y, the first switch 691 is activated while theconfirmation affordance 634C is highlighted. In some embodiments, thefirst device configures (792) a third device to be operated based onuser input from the input device and ceasing to operate the seconddevice based on user input from the input device. Thus, a user can use asingle input device to control more than two devices withoutdisconnecting the input device from the first device and connecting theinput device to the third device, which may be a time-consuming, if notimpossible, process for persons of limited mobility. Using a singleinput device to control multiple devices reduces costs for the user (asthey need not purchase multiple input devices). For example, in FIG. 6Z,the first device display a first transferred control notification 642Aindicating that a third device (e.g., the media player 503) is operatedbased on user input from the input device.

It should be understood that the particular order in which theoperations in FIGS. 7A-7G have been described is merely example and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

In accordance with some embodiments, FIG. 8 shows a functional blockdiagram of an electronic device 800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 8 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 8, a first electronic device 800 includes a displayunit 802 configured to display a user interface and an input deviceinterface 804 configured to receive user input, and a processing unit810 coupled with the display unit 802 and the input device interface804. In some embodiments, the processing unit 1310 includes: a displaycontrol unit 812, an input receiving unit 814, an operationalconfiguration unit 816, and an alert generation unit 818.

The processing unit 810 is configured to display (e.g., with the displaycontrol unit 812), on the display unit 802, a device control transferaffordance while operating the first device based on user input from aninput device that is in communication with the first device (e.g., viathe input device interface 804). The processing unit 810 is configuredto receive a device control transfer user input from the input device(e.g., with the input receiving unit 814 via the input device interface804) selecting the device control transfer affordance that is displayedon the display unit 802 of the first electronic device 800. In responseto receiving the device control transfer user input, the processing unit810 is configured to configure a second electronic device (e.g., withthe operational configuration unit 816) to be operated based on userinput from the input device and ceasing to operate the first devicebased on user input from the input device.

In some embodiments, the processing unit 810 is configured to operatethe first electronic device based on the user input from the inputdevice (e.g., with the input receiving unit 814) by operating the firstdevice in an accessibility mode of operation.

In some embodiments, user input from the input device (e.g., via theinput device interface 804) includes switch inputs. In some embodiments,at least one of the switch inputs is generated by a switch deviceincluding one or more switches and designed for use by users who areunable to use the standard input device(s) of the first electronicdevice 800. In some embodiments, at least one of the switch inputs isgenerated by an input device of the first electronic device 800 (coupledto the input device interface 804). For example, in some embodiments, atleast one of the switch inputs is generated by a touch-sensitive surfaceof the first electronic device 800 (coupled to the input deviceinterface 804). For example, in some embodiments, at least one of theswitch inputs is generated by a camera of the first electronic device800 (coupled to the input device interface 804).

In some embodiments, the processing unit 810 is configured to displaythe device control transfer affordance by displaying (e.g., with thedisplay control unit 812), on the display unit 802, a scan affordancewhile operating the first electronic device based on the user input fromthe input device. In some embodiments, the processing unit 810 isconfigured to display the device control transfer affordance byreceiving (e.g., with the input receiving unit 814) a scan user inputfrom the input device selecting the scan affordance. In someembodiments, the processing unit 810 is configured to display the devicecontrol transfer affordance by displaying (e.g., with the displaycontrol unit 812), on the display unit 802, one or more device selectaffordances while operating the first device, the one or more deviceselect affordances including a second device affordance associated witha second device. In some embodiments, the processing unit 810 isconfigured to display the device control transfer affordance byreceiving (e.g., with the input receiving unit 814) a device select userinput from the input device selecting the second device affordance. Insome embodiments, the processing unit 810 is configured to display thedevice control transfer affordance in response to receiving the deviceselect user input.

In some embodiments, the processing unit 810 is configured to displaythe display control transfer affordance by displaying (e.g., with thedisplay control unit 812), on the display unit 802, a first transferconfirmation notification indicating that the input device will be usedto operate the second electronic device upon selection of the devicecontrol transfer affordance.

In some embodiments, the processing unit 810 is configured to displaythe device control transfer affordance by causing display (e.g., withthe display control unit 812), on a display unit of the secondelectronic device, a second transfer confirmation notificationindicating that the input device will be used to operate the secondelectronic device upon selection, on the first electronic device, of thedevice control transfer affordance.

In some embodiments, the processing unit 810 is configured to configurethe second electronic device to be operated based on user input from theinput device by configuring the second electronic device (e.g., with theoperational configuration unit 816) to operate in the same accessibilitymode of operation as the first electronic device.

In some embodiments, the processing unit 810 is configured to configurethe second electronic device to be operated based on user input from theinput device by forwarding (e.g., with the operational configurationunit 816) inputs from the input device to the second electronic device.In some embodiments, the processing unit 810 is configured to configurethe second electronic device to be operated based on user input from theinput device by establishing a connection (e.g., with the operationalconfiguration unit 816) between the input device and the secondelectronic device.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), on the display unit 802, afirst transferred control notification indicating that operation of thesecond device (and not the first device) is based on the user input fromthe input device. In some embodiments, the processing unit 810 isconfigured to display (e.g., with the display control unit 812), on adisplay unit of the second electronic device, a second transferredcontrol notification indicating that operation of the second electronicdevice is based on the user input from the input device (and not aninput device of the second electronic device).

In some embodiments, the processing unit 810 is configured to causedisplay (e.g., with the display control unit 812), on a display unit ofthe second electronic device, of a device control return affordancewhile operating the second electronic device based on user input fromthe input device, to receive a device control return user input (e.g.,with the input receiving unit 814) from the input device selecting thedevice control return affordance, and operate (e.g., with theoperational configuration unit 816) the first electronic device 800based on user input from the input device and ceasing to operate thesecond electronic device based on user input from the input device.

In some embodiments, the processing unit 810 is configured to receive(e.g., with the input receiving unit 814) an escape input from the inputdevice matching an escape action and operate (e.g., with the operationalconfiguration unit 816) the first electronic device 800 based on userinput from the input device and ceasing to operate the second electronicdevice based on user input from the input device.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), on the display unit 802, anescape setting user interface including one or more affordances fordefining the escape action.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), on the display unit 802, anaccessibility settings user interface including one or more affordancesfor changing one or more accessibility settings for the secondelectronic device.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), the accessibility settingsuser interface with one or more affordances for changing a scanningspeed or highlight color of a selection indicator on the secondelectronic device.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), the accessibility settingsuser interface with one or more affordances for changing a switch actionof the second electronic device.

In some embodiments, the processing unit 810 is configured to display(e.g., with the display control unit 812), the accessibility settingsuser interface with one or more affordances for changing a backup switchaction of the second electronic device.

In some embodiments, one or more of the accessibility settings for thesecond electronic device are based on one or more accessibility settingsfor the first electronic device 800. In some embodiments, at least oneaccessibility setting for the second electronic device is different thana corresponding accessibility setting for the first electronic device800. In some embodiments, an accessibility setting for the secondelectronic device indicating a switch action for a switch input isdifferent than an accessibility setting for the first electronic device800 indicating a switch action for the switch input.

In some embodiments, the processing unit 810 is configured to generatean alter (e.g., with the alert generation unit 818), at the firstelectronic device 800, while operating the second electronic devicebased on the user input from the input device and cause display (e.g.,with the display control unit 812), on the display unit of the secondelectronic device, of one or more alert response affordances.

In some embodiments, the processing unit 810 is configured to receive adismiss user input (e.g., with the input receiving unit 814) selecting adismiss affordance of the one or more alert response affordances andcease display (e.g., with the display control unit 812) of the one ormore alert response affordances.

In some embodiments, the processing unit 810 is configured to receive areturn user input (e.g., with the input receiving unit 814) selecting areturn affordance of the one or more alert response affordances andoperate the first electronic device 800 (e.g., with the operationalconfiguration unit 816) based on user input from the input device andcease to operate the second electronic device based on user input fromthe input device.

In some embodiments, the processing unit 810 is configured to receive acontinued action user input (e.g., with the input receiving unit 814)selecting a continued action affordance of the one or more alertresponse affordances and operated the second electronic device (e.g.,with the operational configuration unit 816) based on user input fromthe input device to respond to the alert.

In some embodiments, the processing unit 810 is configured to receive aquick action user input (e.g., with the input receiving unit 814)selecting a quick action user input selecting a quick action affordanceof the one or more alert response affordances and dismiss the alert atthe first electronic device 800 and continuing to operate the secondelectronic device based on user input from the input device.

In some embodiments, the processing unit 810 is configured to causedisplay (e.g., with the display control unit 812), of on a display unitof the second electronic device, a third device control transferaffordance while operating the second electronic device based on userinput from the input device, receive (e.g., with the input receivingunit 814) a third device control transfer user input from the inputdevice selecting the third device control transfer affordance, andconfigure (e.g., with the operation configuration unit 816) a thirdelectronic device to operate based on user input from the input deviceand cease to operate the second electronic device based on user inputfrom the input device.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 7A-7G are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 8.For example, display operation 702, receiving operation 728, andconfiguration operation 730 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 receiving a user input from an input device, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether the user input from the input device corresponds to apredefined event or sub-event, such as selection of an object on a userinterface, or rotation of the device from one orientation to another.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: at a first device with oneor more processors, non-transitory memory, a display: displaying, on thedisplay, a device control transfer affordance while operating the firstdevice based on user input from an input device that is in communicationwith the first device; receiving a device control transfer user inputfrom the input device selecting the device control transfer affordancethat is displayed on the display of the first device; and in response toreceiving the device control transfer user input, configuring a seconddevice to be operated based on user input from the input device andceasing to operate the first device based on user input from the inputdevice.
 2. The method of claim 1, wherein operating the first devicebased on the user input from the input device includes operating thefirst device in an accessibility mode of operation and operating thesecond device based on the user input from the input device includesoperating the second device in the same accessibility mode of operation.3. The method of claim 2, wherein operating the second device in theaccessibility mode is performed without interaction with an input deviceof the second device.
 4. The method of claim 1, wherein user inputs withthe input device are switch inputs.
 5. The method of claim 4, wherein atleast one of the switch inputs is generated by a dedicated switch devicethat includes one or more switches and is designed for use by users whoare unable to use the standard input devices of the first device and/orthe second device.
 6. The method of claim 4, wherein at least one of theswitch inputs is generated by an input device of first device.
 7. Themethod of claim 6, wherein at least one of the switch inputs isgenerated by a touchscreen of the first device.
 8. The method of claim4, wherein at least one of the switch inputs is generated by a camera.9. The method of claim 1, further comprising: displaying, on thedisplay, one or more device select affordances while operating the firstdevice based on the first user input from the input device, the one ormore device select affordances including a second device affordanceassociated with the second device; receiving a device select user inputfrom the input device selecting the second device affordance; and inresponse to the device select user input, displaying the device controltransfer affordance on the display of the first device.
 10. The methodof claim 9, further comprising, in response to receiving the deviceselect user input, displaying, on the display, a first transferconfirmation notification indicating that the input device will be usedto operate the second device upon selection of the device controltransfer affordance.
 11. The method of claim 9, further comprising, inresponse to receiving the device select user input, causing display, ona display of the second device, a second transfer confirmationnotification that indicates that the input device will be used tooperate the second device upon confirmation of the selection on thefirst device.
 12. The method of claim 9, further comprising: displaying,on the display, a scan affordance while operating the first device basedon the user input from the input device; receiving a scan user inputfrom the input device selecting the scan affordance; and in response toreceiving the scan user input, displaying, on the display, the one ormore device select affordances.
 13. The method of claim 1, furthercomprising, displaying, on the display, a first transferred controlnotification indicating that operation of the second device is based onthe user input from the input device.
 14. The method of claim 1, furthercomprising, causing display, on a display of the second device, a secondtransferred control notification indicating that operation of the seconddevice is based on the user input from the input device.
 15. The methodof claim 1, further comprising: causing display, on a display of thesecond device, of a device control return affordance while operating thesecond device based on the user input from the input device; receiving adevice control return user input from the input device selecting thedevice control return affordance; and in response to receiving thedevice control return user input, operating the first device based onuser input from the input device and ceasing to operate the seconddevice based on user input from the input device.
 16. The method ofclaim 1, further comprising: causing display, on a display of the seconddevice, of a third device control transfer affordance while operatingthe second device based on the user input from the input device;receiving a third device control transfer user input from the inputdevice selecting the third device control transfer affordance; and inresponse to receiving the third device control transfer user input,configuring a third device to be operated based on user input from theinput device and ceasing to operate the second device based on userinput from the input device.
 17. The method of claim 1, furthercomprising: receiving an escape input from the input device matching anescape action; and in response to receiving the escape input, operatingthe first device based on user input from the input device and ceasingto operate the second device based on user input from the input device.18. The method of claim 17, further comprising, displaying, on thedisplay, an escape settings user interface including one or moreaffordances for defining the escape action.
 19. The method of claim 1,further comprising: generating an alert at the first device whileoperating the second device based on the second user input from theinput device; and in response to the alert, causing display, at thesecond device, of one or more alert response affordances.
 20. The methodof claim 19, further comprising: receiving a dismiss user inputselecting a dismiss affordance of the one or more alert responseaffordances; and in response to receiving the dismiss user input,ceasing display of the one or more alert response affordances.
 21. Themethod of claim 19, further comprising: receiving a return user inputselecting a return affordance of the one or more alert responseaffordances; and in response to receiving the return user input,operating the first device based on user input from the input device andceasing to operate the second device based on user input from the inputdevice.
 22. The method of claim 19, further comprising: receiving acontinued action user input selecting a continued action affordance ofthe one or more alert response affordances; and in response to receivingthe continued action user input, operating the second device based onuser input from the input device to respond to the alert.
 23. The methodof claim 19, further comprising: receiving a quick action user inputselecting the quick action affordance of the one or more alert responseaffordances; and in response to receiving the quick action user input,dismissing the alert and continuing to operate the second device basedon user input from the input device.
 24. The method of claim 1, whereinoperating the second device based on the user input from the inputdevice is based on one or more accessibility settings for the seconddevice, further comprising, displaying, on the display, an accessibilitysettings user interface including one or more affordances for changingthe one or more accessibility settings for the second device.
 25. Themethod of claim 24, wherein the accessibility settings user interfaceincludes one or more affordances for changing a scanning speed or ahighlight color of a selection indicator on the second device.
 26. Themethod of claim 24, wherein the accessibility settings user interfaceincludes one or more affordances for changing a switch action of thesecond device.
 27. The method of claim 24, wherein the accessibilitysettings user interface includes one or more affordances for changing abackup switch action of the second device.
 28. The method of claim 24,wherein operating the first device based on the first user input fromthe input device is based on one or more accessibility settings for thefirst device, wherein one or more of the accessibility settings for thesecond device are based on one or more of the accessibility settings forthe first device.
 29. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which, when executed by a first electronic device with adisplay, and an input device, cause the first electronic device to:displaying, on the display, a device control transfer affordance whileoperating the first electronic device based on user input from an inputdevice that is in communication with the first device; receiving adevice control transfer user input from the input device selecting thedevice control transfer affordance that is displayed on the display ofthe first electronic device; and in response to receiving the devicecontrol transfer user input, configuring a second electronic device tobe operated based on user input from the input device and ceasing tooperate the first electronic device based on user input from the inputdevice.
 30. A first electronic device, comprising: a display unitconfigured to display a user interface; and a processing unit coupledwith the display unit, the processing unit configured to: display, onthe display unit, a device control transfer affordance while operatingthe first electronic device based on user input from an input devicethat is in communication with the first electronic device, receive adevice control transfer user input from the input device selecting thedevice control transfer affordance that is displayed on the displayunit; and in response to receiving the device control transfer userinput, configure a second electronic device to be operated based on userinput from the input device and ceasing to operate the first electronicdevice based on user input from the input device.